-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test(forkJoin): add tests with never and with unsubscribing after error #2394
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks really good, overall, just a couple of small requests.
spec/observables/forkJoin-spec.ts
Outdated
hot('------#'), | ||
hot('----------')); | ||
const expected = '------#'; | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we vertically align these marble strings? It's good to make the next developer see the visual alignment of the events.
spec/observables/forkJoin-spec.ts
Outdated
hot('--------------'), | ||
hot('------|') | ||
); | ||
const expected = '------|'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same as the other feedback... vertically align the marbles.
Add tests with Observable that never completes, so that it is clear how forkJoin operator behaves with it. Add test which shows that forkJoin unsubscribes from other Observables when one of them errors.
@Blesh done. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Description:
I am writing docs for
forkJoin
and felt bad making assertions about how it behaves, without having unit tests to back me up.